getrandom: allow GRND_INSECURE flag#13250
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
test/cl919839094
branch
3 times, most recently
from
653ffa5 to
de7d432
Compare
Because we fetch from urandom under the assumption that the host urandom has sufficient entropy, we can allow and silently ignore GRND_INSECURE for the same reason we currently allow and silently ignore GRND_NONBLOCK. The randomness will be more secure than what was requested, but this is fine. PiperOrigin-RevId: 921880454
copybara-service
Bot
force-pushed
the
test/cl919839094
branch
from
de7d432 to
4b8c953
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
getrandom: allow GRND_INSECURE flag
Because we fetch from urandom under the assumption that the host urandom has
sufficient entropy, we can allow and silently ignore GRND_INSECURE for the
same reason we currently allow and silently ignore GRND_NONBLOCK.
The randomness will be more secure than what was requested, but this is fine.